Split calico go-build image publish into parallel pipelines #636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change breaks calico/go-build image build and push to DockerHub into parallel runs. The sequential run for all supported architectures will take about an hour to complete. Moving to parallel pipelines reduce total time to 15-20 minutes. It also switches semaphore runners to
f1-standard-2
(fromf1-standard-4
) because we have 4x more -2 runners and the CI time for each pipeline is only ~4 minutes longer.